refactor(iroh)!: rework net_report#3314
Conversation
4ddd06b to
7f985bb
Compare
bb2c8fb to
0fddf40
Compare
|
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3314/docs/iroh/ Last updated: 2025-06-24T13:03:46Z |
f9bacd4 to
e9e7bc3
Compare
|
|
e807b2b to
d4f3740
Compare
a0c876d to
3610be3
Compare
ramfox
left a comment
There was a problem hiding this comment.
run_until_cancelled_owned, reducing the probes, and cleaning up to net_report::Client makes this much more easy to reason about.
I'd argue we still have a bit of cleanup around the probe plan creation, but this is a long-needed change!
d09c878 to
85e6939
Compare
303dce9 to
542361e
Compare
thanks for checking this, the reason we exit is because |
Hmm, it is certainly possible for the two to differ, and I could see us optimizing the differences in the future, but for now I think this should "just work out", as the latencies we will get from these QADs will be the ones returned in every run, and subsequently used for evaluation |
ref n0-computer/iroh#3314 --------- Co-authored-by: Asmir Avdicevic <asmir.avdicevic64@gmail.com>
Description
Watchablein more placesSTUNfunctionality from the relay serverFixes
Breaking Changes
iroh_relay::protos::stun::StunErroriroh_relay::server::testing::stun_configiroh_relay::protos::stuniroh_relay::quic::QuicClient::get_addr_and_latencyDEFAULT_STUN_PORTDepends on